home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
padc.z
/
padc
Wrap
Text File
|
1998-10-20
|
11KB
|
199 lines
PPPPAAAADDDDCCCC((((1111)))) PPPPAAAADDDDCCCC((((1111))))
NNNNAAAAMMMMEEEE
_pppp_aaaa_dddd_cccc - process activity data collector
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
_pppp_aaaa_dddd_cccc _----_ssss_rrrr_kkkk [_----_IIII _l_e_n] [_----_hhhh _p_r_i] [_----_bbbb _b_u_f_s_z] [_----_tttt _t_i_m_e]
_pppp_aaaa_dddd_cccc _----_ssss_rrrr_kkkk [_----_iiii] [_----_IIII _l_e_n] [_----_hhhh _p_r_i] [_----_bbbb _b_u_f_s_z] [_----_tttt _t_i_m_e]
[_----_pppp _p_i_d]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_pppp_aaaa_dddd_cccc traces the activity of a process or group of processes and writes
the raw event data to the standard output. System calls, scheduling
actions, and disk i/o operations are activities that _pppp_aaaa_dddd_cccc can trace. In
addition to kernel-generated events, _pppp_aaaa_dddd_cccc collects any events created by
processes through the _rrrr_tttt_mmmm_oooo_nnnn______llll_oooo_gggg______uuuu_ssss_eeee_rrrr______tttt_ssss_tttt_aaaa_mmmm_pppp(3) library routine.
_pppp_aaaa_dddd_cccc is normally invoked by the _pppp_aaaa_rrrr(1) program which reads and formats
its output. _pppp_aaaa_dddd_cccc can also be invoked by itself with the event data
written to a file for later processing by _pppp_aaaa_rrrr or _rrrr_tttt_mmmm_oooo_nnnn_----_dddd_uuuu_mmmm_pppp(1).
By default, _pppp_aaaa_dddd_cccc traces the requested events for all processes on a
system. System call event collection can be restricted to a specific set
of processes with one or more ----pppp options. If the ----iiii option is given, all
future children of the specified processes will also have their system
calls traced. If the ----tttt option is specified, _pppp_aaaa_dddd_cccc will collect trace
data for a limited amount of time.
_pppp_aaaa_dddd_cccc collects trace data until: the time specified with the ----tttt option has
elapsed, _pppp_aaaa_dddd_cccc receives a SSSSIIIIGGGGIIIINNNNTTTT or a SSSSIIIIGGGGHHHHUUUUPPPP signal, or all processes to
be traced have terminated.
The execution of traced processes is not affected when _pppp_aaaa_dddd_cccc is collecting
event data.
OOOOPPPPTTTTIIIIOOOONNNNSSSS
----bbbb _b_u_f_s_z Use a buffer _b_u_f_s_z bytes large to buffer event data written to
the standard output. By default _pppp_aaaa_dddd_cccc buffers up to 128
Kilobyte of data before writing the data to the standard
output. Setting _b_u_f_s_z to zero causes _pppp_aaaa_dddd_cccc to buffer its output
as little as possible.
----hhhh _p_r_i Run _pppp_aaaa_dddd_cccc with a nondegrading realtime scheduling priority _p_r_i.
By default _p_a_d_c tries to use the same realtime scheduling
priority that the system event collection process uses. This
will only happen if _p_a_d_c is started by the super-user. _p_a_d_c
tries to match scheduling priority so that it can compete
equally for CPU time when doing system-wide event collection.
----kkkk Trace all disk i/o operations on the system.
PPPPaaaaggggeeee 1111
PPPPAAAADDDDCCCC((((1111)))) PPPPAAAADDDDCCCC((((1111))))
----IIII _m_a_x Set the maximum amount of data returned by the kernel for
indirect parameter values returned with a system call event.
Some system calls (e.g. _rrrr_eeee_aaaa_dddd) have potentially lots of data
associated with them. _pppp_aaaa_dddd_cccc always collects direct system call
arguments; this option can be used to control the amount of
indirect data. If _m_a_x is 0, then no indirect parameter values
will be collected. Otherwise _m_a_x can be any value up to a
maximum determined by the operating system; by default 4096
bytes. Note that setting this value to a large number
increases the probability of losing events.
----iiii Inherit system call tracing to future children of the processes
specified with ----pppp options.
----pppp _p_i_d Enable system call event tracing for the specified _p_i_d. This
option may be specified multiple times to enable system call
tracing for multiple processes. Processes specified with this
option must belong to the current user unless the user has
super-user privilege.
----rrrr Trace scheduling events for all processes on the system.
----ssss Trace system calls for processes specified with the ----pppp and ----iiii
options.
----tttt _t_i_m_e Collect data for a _t_i_m_e-second interval.
NNNNOOOOTTTTEEEESSSS
_pppp_aaaa_dddd_cccc reads its information from the _rrrr_tttt_mmmm_oooo_nnnn_dddd(1) server process on the
machine where the traced processes are located. The _rrrr_tttt_mmmm_oooo_nnnn_----_cccc_llll_iiii_eeee_nnnn_tttt(1)
program may be used to collect trace data from an _rrrr_tttt_mmmm_oooo_nnnn_dddd process on a
different machine; the only restriction is that you cannot (easily)
collect system call event data.
_pppp_aaaa_dddd_cccc's main task is to merge multiple streams of event data that are
collected on multi-processor systems. This work may require a
significant amount of memory if the system is heavily loaded because much
event data may need to be buffered to insure events are properly sorted
by time. For this reason _pppp_aaaa_dddd_cccc does not merge event data when doing
system-wide event collection; instead _pppp_aaaa_rrrr recognizes that it needs to
sort-merge the event data when displaying event traces (since it
typically is run after the event data has been collected).
Event data collected by _pppp_aaaa_dddd_cccc is time stamped with a high resolution
timer. The resolution of this timer depends on the system hardware; this
value is recorded in the event stream so that post-processing programs
such as _pppp_aaaa_rrrr can properly calculate time values.
To reduce system load, system call events generated by _pppp_aaaa_dddd_cccc itself are
not recorded. This can lead to some inexplicable gaps in the schedule
trace.
PPPPaaaaggggeeee 2222
PPPPAAAADDDDCCCC((((1111)))) PPPPAAAADDDDCCCC((((1111))))
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
_U_n_a_b_l_e _t_o _c_o_n_t_a_c_t _r_t_m_o_n _s_e_r_v_i_c_e _o_n _l_o_c_a_l _h_o_s_t. There is no _rrrr_tttt_mmmm_oooo_nnnn_dddd server
process running on the system. Usually this is because the rtmond
service has been disabled; consult _cccc_hhhh_kkkk_cccc_oooo_nnnn_ffff_iiii_gggg(1M).
_C_a_n_n_o_t _r_e_a_c_h _r_t_m_o_n _s_e_r_v_i_c_e _o_n _l_o_c_a_l _h_o_s_t, _a_c_c_e_s_s _d_e_n_i_e_d. The _rrrr_tttt_mmmm_oooo_nnnn_dddd
server process has been configured to deny access to all users on the
local host.
_U_n_a_b_l_e _t_o _s_t_a_r_t _d_a_t_a _c_o_l_l_e_c_t_i_o_n; _s_e_r_v_e_r _d_i_s_a_l_l_o_w_e_d _e_v_e_n_t _c_o_l_l_e_c_t_i_o_n. The
_rrrr_tttt_mmmm_oooo_nnnn_dddd server process has been configured to restrict the set of events
that may be collected and you have requested collection of events that
are unavailable.
_U_n_a_b_l_e _t_o _s_t_a_r_t _d_a_t_a _c_o_l_l_e_c_t_i_o_n; _t_e_m_p_o_r_a_r_i_l_y _o_u_t _o_f _r_e_s_o_u_r_c_e_s. The
_rrrr_tttt_mmmm_oooo_nnnn_dddd server process was unable to start event collection because it ran
out of system resources such as threads or memory.
FFFFIIIILLLLEEEESSSS
_////_dddd_eeee_vvvv_////_pppp_aaaa_rrrr for enabling system call tracing
_////_tttt_mmmm_pppp_////_...._rrrr_tttt_mmmm_oooo_nnnn_dddd______ssss_oooo_cccc_kkkk_eeee_tttt UNIX domain socket for client connections
SSSSEEEEEEEE AAAALLLLSSSSOOOO
_pppp_aaaa_rrrr(1), _rrrr_tttt_mmmm_oooo_nnnn_----_cccc_llll_iiii_eeee_nnnn_tttt(1), _rrrr_tttt_mmmm_oooo_nnnn_----_dddd_uuuu_mmmm_pppp(1), _rrrr_tttt_mmmm_oooo_nnnn_dddd(1), _pppp_aaaa_rrrr(7).
PPPPaaaaggggeeee 3333